Essential View flexibility | Can we have the ability to change Parent view hosting. See scenario and image pls.

[michellevankolck4401]

Dear  Development team,

I would really like to raise awareness around a specific workflow scenario that highlights a significant limitation in Revit that I am hoping can be fixed at some point. I think the industry has just got used to it never working as well as it could and I would like to propose a modification to parent view hosting that could really be helping to the industry in making the modelling and view creation and management process more fluid and flexible. Please vote for this issue. I think it's a good wish-list item and has been raised by many fellow team members of the years.

PROCESS OF ISSUE

1. Plan (A) is created. (This is a working view and never intended to be placed on a sheet.)
2. Detail call-out (A) is then also mistakenly draw on Section (A).
3. Detail call-out (B) is then created in another view and is deliberately referenced to Call-out (A). Sometimes a multi-storey building may have identical kitchens or bathrooms and we would reference the detail only once in model but need to refer to that detail in multiple views.
4. Where we get stuck is where we need to MOVE (edit/change the Parent view association) Detail call-out (A) to a different view. At present this parameter setting is locked out and I can’t seem to see any work-around to help teams with this issue.

Note: It makes sense therefore that if Plan (A) Is deleted then both call-out (a) and (B) will be deleted. We have no issue with this behavior but we need to change the Parent view reference of sections or call-outs that are referenced in a view.

COMMON INDUSTRY WORK AROUND

The only solution we have is to have to re-create Detail (A) in new/correct plan view and then re-assign all other call-outs in multiple views to new detail. As you can imagine this workflow is prone to error and risk.

Please see image below. 

Thanks so much for your time!

Michelle

[kimberly_fuhrman-jones]

Congrats! We think this is a great idea, so we've decided to add it to our roadmap. Thanks for the suggestion!

The Factory

[kimberly_fuhrman-jones]

We are pleased to say that this has been implemented in Revit 2022!

-The Factory

[michellevankolck4401]

That's great news. Thanks for hearing our plea 😉

Credit should also go to Craig Rogers and Stephen Taskin who helped clarify the issue and ramification clearly for me too.

[gsucci]

Yes, this is a great addition in 2022!

However, I run a test and I was indeed able to delete a view containing a detail view, and the detail view was not deleted in the project browser.

I am now wondering: this detail view is left "orphaned", because it does not have any reference tag on any view (its Parent was deleted).

I could not find a "designed" way to restore a parent view, and thus, obtain the callout graphics and tag on any compatible view.

Should we just create a new callout where we want it, but reference the orphaned view instead of creating a new view?

thank you

regards

gio

[minjie.wang]

I want to clarify the information. In Revit 2022, we only enable the ability to preserve the callout view when the parent view is deleted. We did not provide the ability to switch the parent view on a callout view. So that when the parent view was deleted, the callout view would show as "independent" and cannot host on a new parent view. I will suggest to recreate a new callout view referencing to a new parent view, instead of referring to the previous independent callout view.

This request is still open and under internal review. @kimberly_fuhrman-jones I will suggest to change the status to "under review" or "gathering support", thanks!

[kimberly_fuhrman-jones]

Thank you for the clarification, @minjie.wang ! We can consider this one "Still Improving"!

[kimberly_fuhrman-jones]

Here we go again! This has been added to our new Roadmap! Thank you again for your Idea submission!

-The Factory

[pieterschiettecatte]

Very glad to see this is was added to the roadmap! Ideally the 'parent view' parameter becomes a regular dropdown in which we can select another view (or set it to independent). 

[mauricio_mssf]

When we create a callout it is linked to a view, it would be nice to have the option to change the parent view to be linked to another view, without having to recreate everything from scratch again.

Currently we only have the option to link this view to the created view or to none at all.

[Mike.FORM]

I was not able to find it in the roadmap, but hopefully this gets implemented.

If you have a callout that displays on intersecting views, it should have all those views listed in the "Parent View" dropdown in properties so that it can be changed if needed. Currently it only lists the View it was created in or <none>.

MikeFORM_0-1701204135367.png